<!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:0; mso-generic-font-family:roman; mso-font-pitch:variable; mso-font-signature:-1610611985 1107304683 0 0 159 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} @font-face {font-family:Consolas; panose-1:2 11 6 9 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:modern; mso-font-pitch:fixed; mso-font-signature:-1610611985 1073750091 0 0 159 0;} @font-face {font-family:Verdana; panose-1:2 11 6 4 3 5 4 4 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:536871559 0 0 0 415 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin:0cm; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi; mso-fareast-language:EN-US;} a:link, span.MsoHyperlink {mso-style-noshow:yes; mso-style-priority:99; color:blue; mso-themecolor:hyperlink; text-decoration:underline; text-underline:single;} a:visited, span.MsoHyperlinkFollowed {mso-style-noshow:yes; mso-style-priority:99; color:purple; mso-themecolor:followedhyperlink; text-decoration:underline; text-underline:single;} p.MsoPlainText, li.MsoPlainText, div.MsoPlainText {mso-style-noshow:yes; mso-style-priority:99; mso-style-link:"Plain Text Char"; margin:0cm; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.5pt; font-family:Consolas; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi; mso-fareast-language:EN-US;} span.PlainTextChar {mso-style-name:"Plain Text Char"; mso-style-noshow:yes; mso-style-priority:99; mso-style-unhide:no; mso-style-locked:yes; mso-style-link:"Plain Text"; mso-ansi-font-size:10.5pt; mso-bidi-font-size:10.5pt; font-family:Consolas; mso-ascii-font-family:Consolas; mso-hansi-font-family:Consolas;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi; mso-fareast-language:EN-US;} .MsoPapDefault {mso-style-type:export-only; margin-bottom:10.0pt; line-height:115%;} @page Section1 {size:612.0pt 792.0pt; margin:70.85pt 70.85pt 70.85pt 70.85pt; mso-header-margin:36.0pt; mso-footer-margin:36.0pt; mso-paper-source:0;} div.Section1 {page:Section1;} --> We've made some change in our organisation. Basically the exchange 2007 server was installed on WM (including db :/ ). There's 2 weeks ago the wm server crashed, and the exchange also crashed, with some db unrecoverable. Now the exchange server is located on a strong physical server, the organization is ok, db recovered ( except one ). We've now some stranges issues : - for one sender the character encoding is doesn't work, and the mail appear without sender, without subject, without attachment, and the header looks like that : Message-ID: <34684148422893@les-raisting>?? From:<sender> <sender@SkyFile.com> To: <recipient> CC: < other recipient> Subject: <subject message> Date: Thu, 26 Nov 2009 16:31:27 +0000 MIME-Version: 1.0 X-Mailer: SkyFile-Gateway (V2.36) Content-Type: text/plain; charset="iso-8859-5" Content-Transfer-Encoding: 8bit Return-Path: <sender> @SkyFile.com X-MS-Exchange-Organization-OriginalArrivalTime: 26 Nov 2009 16:34:02.2679 (UTC) X-MS-Exchange-Organization-AuthSource: <myserver.mydomain.com> X-MS-Exchange-Organization-AuthAs: Anonymous X-MS-Exchange-Organization-OriginalSize: 871 Another issue: In the organisation, in the past, where an 2003 exchange server, who was removed there's some years to install instead an 2007. Now when i do the '' health test '' in the Toolbox- > Best Practice Analyze, the log show a lot of error concerning firt routing groups and it appear that the exchange 2003 is still present in AD, but the server physically doesn't exists anymore. Then my two question are : - What can i do concerning the encoding type ? - how can i remove all information about the exchange 2003 without this server ?

Please post the exact EXBPA errors.If the first issue only affects one user, I would be tempted to simply move his mailbox to another store and test or mail-disable and re-mail enable his account without knowing more.

What i've copy/past is the exact mail header content, no error in the eventlog. Oh, i've forgot, it's an public folder email activated, then i can't move it on other db. Then in this pb, its the only one sub-folder email based wich i've this issue. In fact the sender is a ship ( i'm in a shipping society) who have then adresse email ( satelite communication provider ) depending the current localisation of the ship. (skyfile is one of the provider )

Ok, try mail-disabling and reenabling and test.What exactly did ExBpa alert on?

nevermind, understand. i'll try the ExBPA and will get log here if i've an issue.

Here's the problem founds in the ExBpa ( i've lead the health, permission, connectivity, baseline, and readiness check) Topic : Admin Group : First Routing Group - Routing Group : First Routing Group Routing Master has been deleted The nominated routing group master for routing group 'First Routing Group' has been deleted. This may cause mail flow problems. Server name: CN=ABCCHEXSRV\0ADEL:32385622-4927-45d8-ad6a-c3d0b823d75f,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=ABCMARITIME,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=abcmaritime,DC=group. Cannot connect to port 25 of the routing group master Server ABCCHEXSRV\0ADEL:32385622-4927-45d8-ad6a-c3d0b823d75f is a routing group master but a connection to port 25 cannot be established from the workstation where this tool is running. Cannot connect to port 691 of the routing group master Server ABCCHEXSRV\0ADEL:32385622-4927-45d8-ad6a-c3d0b823d75f is a routing group master but a connection to port 691 cannot be established from the workstation where this tool is running. That's the only error found by ExBpa in the health test. Regarding the old 2003 server(ABCCHEXSRV).

On Mon, 30-Nov-09 14:54:37 GMT, danagaz wrote:ve Group,CN=Administrative Groups,CN=ABCMARITIME,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=abcmaritime,DC=group. Cannot connect to port 25 of the routing group master Server ABCCHEXSRV\0ADEL:32385622-4927-45d8-ad6a-c3d0b823d75f is a routing group master but a connection to port 25 cannot be established from the workstation where this tool is running. Cannot connect to port 691 of the routing group master Server ABCCHEXSRV\0ADEL:32385622-4927-45d8-ad6a-c3d0b823d75f is a routing group master but a connection to port 691>cannot be established from the workstation where this tool is running. That's the only error found by ExBpa in the health test. Regarding the old 2003 server(ABCCHEXSRV). What other Exchange 2003 servers are in the "First Routing Group"?Make one of them the routing group master.If you have no E2K3 servers in that routing group then move one intoit and make it the RG master -- or remove the routing group.---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP